NTISthis.com

Evidence Guide: ICTPRG419 - Analyse software requirements

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICTPRG419 - Analyse software requirements

What evidence can you provide to prove your understanding of each of the following citeria?

Gather and confirm client requirements

  1. Confirm the requirements, and the scope, of the project with the client
  2. Gather information regarding requirements via sources of information and business processes
  3. Analyse client requirements, to determine the project scope and the problem context or opportunity faced by the business
  4. Document the client requirements, project’s scope, related problems, and sources of information
Confirm the requirements, and the scope, of the project with the client

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Gather information regarding requirements via sources of information and business processes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse client requirements, to determine the project scope and the problem context or opportunity faced by the business

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document the client requirements, project’s scope, related problems, and sources of information

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse the functional and related non-functional requirements

  1. Map business processes using modelling tools such as unified modelling language (UML)
  2. Determine the opportunities for business process efficiencies
  3. Document functional, and related non-functional, processes
Map business processes using modelling tools such as unified modelling language (UML)

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the opportunities for business process efficiencies

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document functional, and related non-functional, processes

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse the feasibility of a project

  1. Analyse the technical feasibility of the project
  2. Analyse the operational feasibility of the project
  3. Determine the budget and schedule feasibility of the project
  4. Examine how the project will fit within the organisation
Analyse the technical feasibility of the project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Analyse the operational feasibility of the project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Determine the budget and schedule feasibility of the project

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Examine how the project will fit within the organisation

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Develop high-level system solutions

  1. Develop and document feasible solutions for client requirements
  2. Explore and document the feasibility of each solution
  3. Examine alternatives against project constraints
  4. Document assumptions, dependencies and required resources
  5. Produce a project risk analysis
  6. Document future requirements
Develop and document feasible solutions for client requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Explore and document the feasibility of each solution

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Examine alternatives against project constraints

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document assumptions, dependencies and required resources

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Produce a project risk analysis

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Document future requirements

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Prepare and publish the software-requirements documentation

  1. Develop the software-requirements document
  2. Submit the software-requirements report to the appropriate person for project approval
Develop the software-requirements document

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Submit the software-requirements report to the appropriate person for project approval

Completed
Date:

Teacher:		 Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Gather and confirm client requirements

1.1 Confirm the requirements, and the scope, of the project with the client

1.2 Gather information regarding requirements via sources of information and business processes

1.3 Analyse client requirements, to determine the project scope and the problem context or opportunity faced by the business

1.4 Document the client requirements, project’s scope, related problems, and sources of information

2. Analyse the functional and related non-functional requirements

2.1 Map business processes using modelling tools such as unified modelling language (UML)

2.2 Determine the opportunities for business process efficiencies

2.3 Document functional, and related non-functional, processes

3. Analyse the feasibility of a project

3.1 Analyse the technical feasibility of the project

3.2 Analyse the operational feasibility of the project

3.3 Determine the budget and schedule feasibility of the project

3.4 Examine how the project will fit within the organisation

4. Develop high-level system solutions

4.1 Develop and document feasible solutions for client requirements

4.2 Explore and document the feasibility of each solution

4.3 Examine alternatives against project constraints

4.4 Document assumptions, dependencies and required resources

4.5 Produce a project risk analysis

4.6 Document future requirements

5. Prepare and publish the software-requirements documentation

5.1 Develop the software-requirements document

5.2 Submit the software-requirements report to the appropriate person for project approval

Required Skills and Knowledge

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Gather and confirm client requirements

1.1 Confirm the requirements, and the scope, of the project with the client

1.2 Gather information regarding requirements via sources of information and business processes

1.3 Analyse client requirements, to determine the project scope and the problem context or opportunity faced by the business

1.4 Document the client requirements, project’s scope, related problems, and sources of information

2. Analyse the functional and related non-functional requirements

2.1 Map business processes using modelling tools such as unified modelling language (UML)

2.2 Determine the opportunities for business process efficiencies

2.3 Document functional, and related non-functional, processes

3. Analyse the feasibility of a project

3.1 Analyse the technical feasibility of the project

3.2 Analyse the operational feasibility of the project

3.3 Determine the budget and schedule feasibility of the project

3.4 Examine how the project will fit within the organisation

4. Develop high-level system solutions

4.1 Develop and document feasible solutions for client requirements

4.2 Explore and document the feasibility of each solution

4.3 Examine alternatives against project constraints

4.4 Document assumptions, dependencies and required resources

4.5 Produce a project risk analysis

4.6 Document future requirements

5. Prepare and publish the software-requirements documentation

5.1 Develop the software-requirements document

5.2 Submit the software-requirements report to the appropriate person for project approval

Evidence of the ability to:

Analyse client requirements to create a software requirements document, including:

gathering, confirming and documenting client requirements

analysing functional and related non-functional requirements, and project feasibility

developing high-level system solutions

submitting documents for approval.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

identify the client business domain

describe content features, such as clarity and readability

summarise the system's current functions

explain document design and usability

explain the functions and features, of templates and style guides

summarise instructional design principles

describe the role of stakeholders and the degree of stakeholder involvement

explain two or more current industry systems development methodologies.